Please mark which AI tools you used for this PR by checking the appropriate boxes:

• GitHub Copilot
• Cursor
• ChatGPT
• Tabnine
• JetBrains AI Assistant
• VSCode IntelliCode
• Claude
• Gemini
• Other AI tool
• No AI tools were used

Tip: If you want to avoid this comment in the future, you can add a label of the format 🤖 ai-* when creating your PR.

@PavelLinearB FYI, I'm unable to respond to the microsurvey, it's uneditable for me.

@PavelLinearB FYI, I'm unable to respond to the microsurvey, it's uneditable for me.

I think it's because you don't have write permissions to the repo.. We'll fix that

@PavelLinearB The check_local_links automation is firing but it's a false positive because this is a README. Do we need to change the rule to not label *.md? Let me know how you'd like to fix.

Also, is check_local_links on the gitStream docs? I don't see an example of that there.

@PavelLinearB The check_local_links automation is firing but it's a false positive because this is a README. Do we need to change the rule to not label *.md? Let me know how you'd like to fix.

Also, is check_local_links on the gitStream docs? I don't see an example of that there.

@azigler, This automation we added to protect our docs from internal links pointing to localhost, so it should be applied to README files. We should fix it to remove this false positive, and we can add it to our catalog.

@PavelLinearB In this case, what's triggering the automation was already there (the URL for a user's locally built docs server) and I didn't add it. How do you recommend we point them to their localhost for their docs if we cannot use a local link? I can remove the URL but that feels less helpful.

@azigler I have changed the check so it ignore the specific REAME line, see #731